Skip to content

fix: allow null issue server ids in websocket broadcasts#45

Merged
itz4blitz merged 1 commit intomasterfrom
hotfix/0.6.3-ci-fix
Mar 30, 2026
Merged

fix: allow null issue server ids in websocket broadcasts#45
itz4blitz merged 1 commit intomasterfrom
hotfix/0.6.3-ci-fix

Conversation

@itz4blitz
Copy link
Copy Markdown
Owner

Summary

  • fix the post-release CI regression by allowing issue websocket broadcasts to handle nullable server ids from persisted issue rows
  • keep room broadcasting guarded so only non-empty server ids are used for room names

Validation

  • pnpm --filter @logarr/backend typecheck
  • pnpm --filter @logarr/backend test
  • pnpm typecheck
  • NODE_ENV=production pnpm exec dotenv -e .env -- pnpm --filter frontend build

@itz4blitz itz4blitz merged commit 26c462c into master Mar 30, 2026
3 checks passed
@itz4blitz itz4blitz deleted the hotfix/0.6.3-ci-fix branch March 30, 2026 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant